|
Requirements engineering (RE) refers to the process of defining, documenting and maintaining requirements to the sub-fields of systems engineering and software engineering concerned with this process. The first use of the term 'requirements engineering' was probably in 1979 in a TRW technical report〔(Software Requirements Engineering Methodology (Development) ) Alford, M. W. and Lawson,J. T. TRW Defense and Space Systems Group. 1979.〕 but did not come into general use until the 1990s with the publication of an IEEE Computer Society tutorial and the establishment of a conference series on requirements engineering that has evolved into the current International Requirements Engineering Conference. In the waterfall model, requirements engineering is presented as the first phase of the development process. Later software development methods, including the Rational Unified Process (RUP), extreme programming (XP) and Scrum assume that requirements engineering continues through the lifetime of a system. Alan M. Davis maintains an extensive bibliography of requirements engineering.〔(Requirements bibliography ) Reviewed November 10th 2011〕 Requirements management which is a sub-function of Systems Engineering practices are also indexed in the INCOSE (International Council on Systems Engineering) manuals. == Requirements engineering activities == The activities involved in requirements engineering vary widely, depending on the type of system being developed and the specific practices of the organization(s) involved. These may include: #Requirements inception or requirements elicitation - #Requirements identification - identifying new requirements #Requirements analysis and negotiation - checking requirements and resolving stakeholder conflicts #Requirements specification (software requirements specification; SRS) - documenting the requirements in a requirements document #System modeling - deriving models of the system, often using a notation such as the Unified Modeling Language (UML) #Requirements validation - checking that the documented requirements and models are consistent and meet stakeholder needs #Requirements management - managing changes to the requirements as the system is developed and put into use These are sometimes presented as chronological stages although, in practice, there is considerable interleaving of these activities. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Requirements engineering」の詳細全文を読む スポンサード リンク
|